Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4364b8fb4c4020747d53cee957969b70444f2a74254473f9765e6d34fb14cfe

Tx prefix hash: 4b9a6c71fc6565493900e05a427d325bc397f68ad8164cc7a2a0ad4cb7ea4992
Tx public key: e0ed65afe5322c14950ad9bf45849d64dfc6a14c8536c5c7df4fc57488a46075
Timestamp: 1724243991 Timestamp [UCT]: 2024-08-21 12:39:51 Age [y:d:h:m:s]: 00:280:12:42:48
Block: 1092753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200395 RingCT/type: yes/0
Extra: 01e0ed65afe5322c14950ad9bf45849d64dfc6a14c8536c5c7df4fc57488a4607502110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7f472fdb4100e1702a1f791d1b749dead0d832b7e961a5b032667c2421e512b 0.600000000000 1567562 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": 1092763, "vin": [ { "gen": { "height": 1092753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7f472fdb4100e1702a1f791d1b749dead0d832b7e961a5b032667c2421e512b" } } ], "extra": [ 1, 224, 237, 101, 175, 229, 50, 44, 20, 149, 10, 217, 191, 69, 132, 157, 100, 223, 198, 161, 76, 133, 54, 197, 199, 223, 79, 197, 116, 136, 164, 96, 117, 2, 17, 0, 0, 0, 3, 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