Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8dd07cdb268c5d429ca4588f172661e1bab35477d89b0af1378bec5089dd50a

Tx prefix hash: 52fc9ed4f62c7d484f927ab803fd1de8ed434a0a352ac16f87eac96678ffc971
Tx public key: 8e1fe5afaa6d20d3303e6ad6e3ba901d67c246b5f60ef614dcf7b7c24d813af8
Timestamp: 1681907884 Timestamp [UCT]: 2023-04-19 12:38:04 Age [y:d:h:m:s]: 01:268:00:04:38
Block: 741997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 453029 RingCT/type: yes/0
Extra: 018e1fe5afaa6d20d3303e6ad6e3ba901d67c246b5f60ef614dcf7b7c24d813af802110000000275e3f0e9000000000000000000

1 output(s) for total of 2.135286411000 dcy

stealth address amount amount idx
00: 2e4bdabc505c873b42a215d1f2931590b1730b5e1db514b124a19a518e3c1fd8 2.135286411000 1188946 of 0

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": 742007, "vin": [ { "gen": { "height": 741997 } } ], "vout": [ { "amount": 2135286411, "target": { "key": "2e4bdabc505c873b42a215d1f2931590b1730b5e1db514b124a19a518e3c1fd8" } } ], "extra": [ 1, 142, 31, 229, 175, 170, 109, 32, 211, 48, 62, 106, 214, 227, 186, 144, 29, 103, 194, 70, 181, 246, 14, 246, 20, 220, 247, 183, 194, 77, 129, 58, 248, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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