Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e485a834fd05e8816e13e7cc0840baeffa7113bb5e0bea0e8336036727d4c7e4

Tx prefix hash: a54faccd5074c9a1f4547961db93eda3cd7bbf2216d55b92ed5e1eb9b31a49a5
Tx public key: 8e1fc43c680ee272f3e2a9ddc0298311360bbb4d6e62d700c91f7bb990b07e78
Timestamp: 1718521868 Timestamp [UCT]: 2024-06-16 07:11:08 Age [y:d:h:m:s]: 00:221:22:16:24
Block: 1045314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158752 RingCT/type: yes/0
Extra: 018e1fc43c680ee272f3e2a9ddc0298311360bbb4d6e62d700c91f7bb990b07e7802110000000136ea7c8b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd8b547667dd3a338edd71f25e692aab0c9157061aa0b5e566be007fac8df874 0.600000000000 1514851 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": 1045324, "vin": [ { "gen": { "height": 1045314 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd8b547667dd3a338edd71f25e692aab0c9157061aa0b5e566be007fac8df874" } } ], "extra": [ 1, 142, 31, 196, 60, 104, 14, 226, 114, 243, 226, 169, 221, 192, 41, 131, 17, 54, 11, 187, 77, 110, 98, 215, 0, 201, 31, 123, 185, 144, 176, 126, 120, 2, 17, 0, 0, 0, 1, 54, 234, 124, 139, 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