Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ff4ea08f582f0bcb39851ab7e0a65c1612300d0b74423dbf66b7fb90a0beb33

Tx prefix hash: 3b4851647d3fbc75d16ce6e2f10cc60369b030157cbf56a599c8397273511abc
Tx public key: 71c0561079d392cf2ea84059ec9c2a70f816184bab057cff2c81211893af6c5a
Timestamp: 1705598543 Timestamp [UCT]: 2024-01-18 17:22:23 Age [y:d:h:m:s]: 01:099:03:32:39
Block: 938145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331969 RingCT/type: yes/0
Extra: 0171c0561079d392cf2ea84059ec9c2a70f816184bab057cff2c81211893af6c5a02110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b301336a6787c7f5b2f5fee161cb0e5b0763aa48eb7ab32acb0ae8392941b147 0.600000000000 1396211 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": 938155, "vin": [ { "gen": { "height": 938145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b301336a6787c7f5b2f5fee161cb0e5b0763aa48eb7ab32acb0ae8392941b147" } } ], "extra": [ 1, 113, 192, 86, 16, 121, 211, 146, 207, 46, 168, 64, 89, 236, 156, 42, 112, 248, 22, 24, 75, 171, 5, 124, 255, 44, 129, 33, 24, 147, 175, 108, 90, 2, 17, 0, 0, 0, 10, 89, 218, 211, 245, 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