Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b809091b8df013ff51be8e14833f9627420de77ebd154dd5a25ab338b45d681c

Tx prefix hash: e98b4e761c65c91ccf8fdc533edc19ef6086a64e9973e18731b8797e3450a451
Tx public key: 556e41b2ce2b3c56198ed8f50fa95807cf10656bbc4f9752fa0fcc574cdd2dbf
Timestamp: 1703029311 Timestamp [UCT]: 2023-12-19 23:41:51 Age [y:d:h:m:s]: 01:323:22:43:54
Block: 916862 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 490372 RingCT/type: yes/0
Extra: 01556e41b2ce2b3c56198ed8f50fa95807cf10656bbc4f9752fa0fcc574cdd2dbf021100000002e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d746cfa8dcc6b4957a995c061a2c5c53dfec482c9e3d8f9b5ede378fc8bed486 0.600000000000 1374424 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": 916872, "vin": [ { "gen": { "height": 916862 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d746cfa8dcc6b4957a995c061a2c5c53dfec482c9e3d8f9b5ede378fc8bed486" } } ], "extra": [ 1, 85, 110, 65, 178, 206, 43, 60, 86, 25, 142, 216, 245, 15, 169, 88, 7, 207, 16, 101, 107, 188, 79, 151, 82, 250, 15, 204, 87, 76, 221, 45, 191, 2, 17, 0, 0, 0, 2, 228, 187, 107, 131, 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