Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57f155f07124adf424afcd6b1de7235c3b1d08dc8542aa006fbf55d62429c8b1

Tx prefix hash: 2079c0a07ae000908f008c374e808902ccbf34a83bbc0260652d0ff43805d217
Tx public key: fe64497a4bee97aa515d1d7af1f319a29caa2247e2fbdc003431d64e8a8e2346
Timestamp: 1721715043 Timestamp [UCT]: 2024-07-23 06:10:43 Age [y:d:h:m:s]: 00:266:12:30:13
Block: 1071761 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190413 RingCT/type: yes/0
Extra: 01fe64497a4bee97aa515d1d7af1f319a29caa2247e2fbdc003431d64e8a8e234602110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 384e8032b2e818eb9cc4703214e557785a885584fe66c2f78780199db600c5e7 0.600000000000 1544108 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": 1071771, "vin": [ { "gen": { "height": 1071761 } } ], "vout": [ { "amount": 600000000, "target": { "key": "384e8032b2e818eb9cc4703214e557785a885584fe66c2f78780199db600c5e7" } } ], "extra": [ 1, 254, 100, 73, 122, 75, 238, 151, 170, 81, 93, 29, 122, 241, 243, 25, 162, 156, 170, 34, 71, 226, 251, 220, 0, 52, 49, 214, 78, 138, 142, 35, 70, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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