Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79572430de01bb10569a2b34ab34a8809608f2df41d32ed423a3817eb8533e49

Tx prefix hash: f65691de2c24d5532665e176021d23e8eb1974c2e7b96645c1d3638748b20c5c
Tx public key: 7a95a0e6d34aedc56cd50f2b190549b84ff9cf4d1ddc8a0d53e7725ac1ff1ab7
Timestamp: 1673053798 Timestamp [UCT]: 2023-01-07 01:09:58 Age [y:d:h:m:s]: 02:051:15:52:34
Block: 669204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 558587 RingCT/type: yes/0
Extra: 017a95a0e6d34aedc56cd50f2b190549b84ff9cf4d1ddc8a0d53e7725ac1ff1ab702110000000571bd5189000000000000000000

1 output(s) for total of 3.720911208000 dcy

stealth address amount amount idx
00: f7157b64ec8df76663c285aae1466d0c3545d70ea8ced3e40a50bc347c14a6f0 3.720911208000 1110507 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": 669214, "vin": [ { "gen": { "height": 669204 } } ], "vout": [ { "amount": 3720911208, "target": { "key": "f7157b64ec8df76663c285aae1466d0c3545d70ea8ced3e40a50bc347c14a6f0" } } ], "extra": [ 1, 122, 149, 160, 230, 211, 74, 237, 197, 108, 213, 15, 43, 25, 5, 73, 184, 79, 249, 207, 77, 29, 220, 138, 13, 83, 231, 114, 90, 193, 255, 26, 183, 2, 17, 0, 0, 0, 5, 113, 189, 81, 137, 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