Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4783f85a6b0d0f213af664f15636d24a5ab1226e32e94cb521a2e4362ddc5a7

Tx prefix hash: d8a0ab8ca07988203c15547b75f191c40beef63807915708335db73aa6be3330
Tx public key: 567de34507aea04aa0b4c42ffd517be6f1f0d59022afc34f6b9138eefc42d4e0
Timestamp: 1698273987 Timestamp [UCT]: 2023-10-25 22:46:27 Age [y:d:h:m:s]: 01:174:23:17:28
Block: 877651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386044 RingCT/type: yes/0
Extra: 01567de34507aea04aa0b4c42ffd517be6f1f0d59022afc34f6b9138eefc42d4e0021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.758539014000 dcy

stealth address amount amount idx
00: e70a208c50c4de8dc36cb8da4a1dcd7e9096094a1193c45e4c727a6696b81405 0.758539014000 1333037 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": 877661, "vin": [ { "gen": { "height": 877651 } } ], "vout": [ { "amount": 758539014, "target": { "key": "e70a208c50c4de8dc36cb8da4a1dcd7e9096094a1193c45e4c727a6696b81405" } } ], "extra": [ 1, 86, 125, 227, 69, 7, 174, 160, 74, 160, 180, 196, 47, 253, 81, 123, 230, 241, 240, 213, 144, 34, 175, 195, 79, 107, 145, 56, 238, 252, 66, 212, 224, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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