Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87b7f089cf300b45c77ac79b02345ca7f11a5de9caa78c4040b1ca44f9c833ae

Tx prefix hash: 81218dc445a7b53f33f38bae1feee90650f889a25ef17148786d94612960cf50
Tx public key: 06909fd3dda14cbaca5a77e3176a3d209a27ad5590b8eb2bd30ff26181b8c9ce
Timestamp: 1733636221 Timestamp [UCT]: 2024-12-08 05:37:01 Age [y:d:h:m:s]: 00:126:21:56:35
Block: 1170512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90512 RingCT/type: yes/0
Extra: 0106909fd3dda14cbaca5a77e3176a3d209a27ad5590b8eb2bd30ff26181b8c9ce021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48e9f7d1a0c99a24610d735706ccc02afd490d01447f1539c9ff959098eb2ce7 0.600000000000 1656243 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": 1170522, "vin": [ { "gen": { "height": 1170512 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48e9f7d1a0c99a24610d735706ccc02afd490d01447f1539c9ff959098eb2ce7" } } ], "extra": [ 1, 6, 144, 159, 211, 221, 161, 76, 186, 202, 90, 119, 227, 23, 106, 61, 32, 154, 39, 173, 85, 144, 184, 235, 43, 211, 15, 242, 97, 129, 184, 201, 206, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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