Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9761a4a83b914c1c025c8e95512d50d6bec1b323c8a4400232223875e65ccfa

Tx prefix hash: 953517b06d9d581e5ac0fd8f6d64879b4413aea21a021f876718698ada9dfb16
Tx public key: f0904f26830897527058496687738aa676ef3d95afd14ef7610bcd63bbd8f997
Timestamp: 1635959652 Timestamp [UCT]: 2021-11-03 17:14:12 Age [y:d:h:m:s]: 03:174:02:00:23
Block: 366608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 902747 RingCT/type: yes/0
Extra: 01f0904f26830897527058496687738aa676ef3d95afd14ef7610bcd63bbd8f99702110000001df56b629f000000000000000000

1 output(s) for total of 37.437133775000 dcy

stealth address amount amount idx
00: cc746bec17aead1d7dc1d86407d36f47b018166852d9c18384c9a1d5b2cd04b7 37.437133775000 744128 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": 366618, "vin": [ { "gen": { "height": 366608 } } ], "vout": [ { "amount": 37437133775, "target": { "key": "cc746bec17aead1d7dc1d86407d36f47b018166852d9c18384c9a1d5b2cd04b7" } } ], "extra": [ 1, 240, 144, 79, 38, 131, 8, 151, 82, 112, 88, 73, 102, 135, 115, 138, 166, 118, 239, 61, 149, 175, 209, 78, 247, 97, 11, 205, 99, 187, 216, 249, 151, 2, 17, 0, 0, 0, 29, 245, 107, 98, 159, 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