Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd51190b984f7c6790a45d1f452061e7e4fb727ed9e76aca616b0cfe3ed347c3

Tx prefix hash: d2f01704d5957f49835b342eac0298194d68eb8002f7a39e4d78121e65f54e74
Tx public key: 0ed4fb965df288b4b3ff0d90c1b5081b71f592eec9171a38c38941f440e3c559
Timestamp: 1733661480 Timestamp [UCT]: 2024-12-08 12:38:00 Age [y:d:h:m:s]: 00:332:18:59:17
Block: 1170724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235329 RingCT/type: yes/0
Extra: 010ed4fb965df288b4b3ff0d90c1b5081b71f592eec9171a38c38941f440e3c559021100000013007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb0cb44bde2a70f6b279215ae36754b95f46b8e1400c104c7f7ef38d6e7d07d0 0.600000000000 1656457 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": 1170734, "vin": [ { "gen": { "height": 1170724 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb0cb44bde2a70f6b279215ae36754b95f46b8e1400c104c7f7ef38d6e7d07d0" } } ], "extra": [ 1, 14, 212, 251, 150, 93, 242, 136, 180, 179, 255, 13, 144, 193, 181, 8, 27, 113, 245, 146, 238, 201, 23, 26, 56, 195, 137, 65, 244, 64, 227, 197, 89, 2, 17, 0, 0, 0, 19, 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