Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ce5bcbfc376cf6692c5c249cabe4d3884ed4624e1b48cc60b1685b3bff92ae1

Tx prefix hash: a645775277f327cfe07246c2d22f0d301878b2f3fbbf96fe2c4f6d61bd6b957b
Tx public key: 5b2079f4d9c3a1fcebaaf62a118022f572d724f9fba254d2ff973f2dde5bad8f
Timestamp: 1725329146 Timestamp [UCT]: 2024-09-03 02:05:46 Age [y:d:h:m:s]: 00:254:01:39:30
Block: 1101738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181450 RingCT/type: yes/0
Extra: 015b2079f4d9c3a1fcebaaf62a118022f572d724f9fba254d2ff973f2dde5bad8f021100000010e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0557316263a2bcd7b946055735a2a7ae8e0dc6c38bcb8ac655adfe6184d73fb6 0.600000000000 1577901 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": 1101748, "vin": [ { "gen": { "height": 1101738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0557316263a2bcd7b946055735a2a7ae8e0dc6c38bcb8ac655adfe6184d73fb6" } } ], "extra": [ 1, 91, 32, 121, 244, 217, 195, 161, 252, 235, 170, 246, 42, 17, 128, 34, 245, 114, 215, 36, 249, 251, 162, 84, 210, 255, 151, 63, 45, 222, 91, 173, 143, 2, 17, 0, 0, 0, 16, 233, 20, 221, 21, 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