Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bb7b4b6bd218b2fd879d52b11fff04a70da0522571e83f30c8c03da78b816f4

Tx prefix hash: 84fa5d4d22a70d403bc316594564e73b8f1e233ba048281bc5c212424617ea26
Tx public key: 067d11ebff02f2c0ad1300347d09a110e7a2d1f41f6185ed17f98b50d51b76c9
Timestamp: 1733283374 Timestamp [UCT]: 2024-12-04 03:36:14 Age [y:d:h:m:s]: 00:115:21:03:39
Block: 1167581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82611 RingCT/type: yes/0
Extra: 01067d11ebff02f2c0ad1300347d09a110e7a2d1f41f6185ed17f98b50d51b76c90211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04fb0a0cceed96d6248831bb89f018d12bfd3ce01527a1bca3f96924da000723 0.600000000000 1653278 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": 1167591, "vin": [ { "gen": { "height": 1167581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04fb0a0cceed96d6248831bb89f018d12bfd3ce01527a1bca3f96924da000723" } } ], "extra": [ 1, 6, 125, 17, 235, 255, 2, 242, 192, 173, 19, 0, 52, 125, 9, 161, 16, 231, 162, 209, 244, 31, 97, 133, 237, 23, 249, 139, 80, 213, 27, 118, 201, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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