Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 584e4458291cb33ac414738df7ff5f62602cdb3d6a4bde0b6a9386837361dab1

Tx prefix hash: 7ce5a13b08d2d3e22cd7be79831004e34c9fec1b4e8337297ea5cb72c3bf0922
Tx public key: ebe94d426689f17015581f32727e01e82635df8a88adb3c650f33a1f30015a21
Timestamp: 1706030343 Timestamp [UCT]: 2024-01-23 17:19:03 Age [y:d:h:m:s]: 01:085:12:39:05
Block: 941713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322233 RingCT/type: yes/0
Extra: 01ebe94d426689f17015581f32727e01e82635df8a88adb3c650f33a1f30015a2102110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb944f4096af1f8964e1bf2bc6c65637701a7a45e526712a41e98ab7a0b0fb7d 0.600000000000 1399869 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 941723, "vin": [ { "gen": { "height": 941713 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb944f4096af1f8964e1bf2bc6c65637701a7a45e526712a41e98ab7a0b0fb7d" } } ], "extra": [ 1, 235, 233, 77, 66, 102, 137, 241, 112, 21, 88, 31, 50, 114, 126, 1, 232, 38, 53, 223, 138, 136, 173, 179, 198, 80, 243, 58, 31, 48, 1, 90, 33, 2, 17, 0, 0, 0, 9, 82, 212, 126, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8