Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96ee72d77840162898f5ec4bd3a783539a9fce98bc176fd549c1a910fc39d951

Tx prefix hash: 5f6577678a7f7d6e01773b6000a9f5e89e945e743461ddd6f23629183eea17ca
Tx public key: e27aeafdb52bf9d6249475c64947f55e2bf564c3a7fbe91c191347d1cf0b9c9a
Timestamp: 1706483135 Timestamp [UCT]: 2024-01-28 23:05:35 Age [y:d:h:m:s]: 00:291:03:45:37
Block: 945471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208475 RingCT/type: yes/0
Extra: 01e27aeafdb52bf9d6249475c64947f55e2bf564c3a7fbe91c191347d1cf0b9c9a02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 280e315fefde793ddcd23ae01e23457cc7740b7fe2eeaf90dc2a3a4cbe9db365 0.600000000000 1403785 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": 945481, "vin": [ { "gen": { "height": 945471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "280e315fefde793ddcd23ae01e23457cc7740b7fe2eeaf90dc2a3a4cbe9db365" } } ], "extra": [ 1, 226, 122, 234, 253, 181, 43, 249, 214, 36, 148, 117, 198, 73, 71, 245, 94, 43, 245, 100, 195, 167, 251, 233, 28, 25, 19, 71, 209, 207, 11, 156, 154, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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