Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb43a8cc231674d4a8d82c38bf10addc46ab76af4f1e03b2ea5096301669ac1b

Tx prefix hash: 9f8420eeb3b8f22bbf535211b6ff0a04cd4c6f9b38c318a56db092bb1c9f07fd
Tx public key: 2c9c6399132533d8920a38cc2c82f6be5f3e7284f66479b9f2b83a64de118235
Timestamp: 1701093126 Timestamp [UCT]: 2023-11-27 13:52:06 Age [y:d:h:m:s]: 01:347:14:13:00
Block: 900805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 507305 RingCT/type: yes/0
Extra: 012c9c6399132533d8920a38cc2c82f6be5f3e7284f66479b9f2b83a64de11823502110000000675e3f0e9000000000000000000

1 output(s) for total of 0.635710047000 dcy

stealth address amount amount idx
00: c0a6413296696b2bf20b539ef2eae8a29b24ac5b7599a9f8c4bbc39778e46a0a 0.635710047000 1357328 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": 900815, "vin": [ { "gen": { "height": 900805 } } ], "vout": [ { "amount": 635710047, "target": { "key": "c0a6413296696b2bf20b539ef2eae8a29b24ac5b7599a9f8c4bbc39778e46a0a" } } ], "extra": [ 1, 44, 156, 99, 153, 19, 37, 51, 216, 146, 10, 56, 204, 44, 130, 246, 190, 95, 62, 114, 132, 246, 100, 121, 185, 242, 184, 58, 100, 222, 17, 130, 53, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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