Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4369f9defbb0f3e577f357904d3e6b9303fe1d68bbaa9bc8a4a85126c15ef95

Tx prefix hash: 29fdd4dde4ab26498e665a99fe1754aad3302aeeee0e372e07eb6542bc3292ed
Tx public key: 458e23a7dd972c0b0ec6dd7b2ba140b366f9011d61fb22f05e963396f9ed8031
Timestamp: 1698277898 Timestamp [UCT]: 2023-10-25 23:51:38 Age [y:d:h:m:s]: 02:058:02:51:56
Block: 877687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 561177 RingCT/type: yes/0
Extra: 01458e23a7dd972c0b0ec6dd7b2ba140b366f9011d61fb22f05e963396f9ed8031021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.758330703000 dcy

stealth address amount amount idx
00: f3a3e85bf632dbe6be4175c30bc29712bb27aebfc0cf480d54193c3f0fe33a18 0.758330703000 1333073 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": 877697, "vin": [ { "gen": { "height": 877687 } } ], "vout": [ { "amount": 758330703, "target": { "key": "f3a3e85bf632dbe6be4175c30bc29712bb27aebfc0cf480d54193c3f0fe33a18" } } ], "extra": [ 1, 69, 142, 35, 167, 221, 151, 44, 11, 14, 198, 221, 123, 43, 161, 64, 179, 102, 249, 1, 29, 97, 251, 34, 240, 94, 150, 51, 150, 249, 237, 128, 49, 2, 17, 0, 0, 0, 2, 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