Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 553de511569cde28f43140711e47866b512629d8a1bb07ce9aa10e8472a00e7d

Tx prefix hash: f7c902c54671e1dc321388ac2bbd5a22f7ff58fea5069223dc97b83e0e7f01f2
Tx public key: cda1a97fad9c1b44da52b1d21cada16eba44b4be0bff0ce8a5731ed62ffc6d83
Timestamp: 1673442919 Timestamp [UCT]: 2023-01-11 13:15:19 Age [y:d:h:m:s]: 02:064:10:08:28
Block: 672434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 567741 RingCT/type: yes/0
Extra: 01cda1a97fad9c1b44da52b1d21cada16eba44b4be0bff0ce8a5731ed62ffc6d8302110000000175e3f0e9000000000000000000

1 output(s) for total of 3.630337243000 dcy

stealth address amount amount idx
00: 12400ac49d4b7e2c51f74e19a88c67a124376fea1c853245399a509b7d1e9476 3.630337243000 1113977 of 0

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": 672444, "vin": [ { "gen": { "height": 672434 } } ], "vout": [ { "amount": 3630337243, "target": { "key": "12400ac49d4b7e2c51f74e19a88c67a124376fea1c853245399a509b7d1e9476" } } ], "extra": [ 1, 205, 161, 169, 127, 173, 156, 27, 68, 218, 82, 177, 210, 28, 173, 161, 110, 186, 68, 180, 190, 11, 255, 12, 232, 165, 115, 30, 214, 47, 252, 109, 131, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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