Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bfc26262ff1c3ddc96133c0f7c4a6e4fc500a6ea5daff546759c6fb368cbe31

Tx prefix hash: 023710c730be5dd41d210e01eeedecc6dd28efda1deb86feaa49d6799dfaade5
Tx public key: fc17684762d16e2b03f06eec8ab97d200aeae85add28a3d816697c83dca1ae49
Timestamp: 1737912295 Timestamp [UCT]: 2025-01-26 17:24:55 Age [y:d:h:m:s]: 01:004:23:20:52
Block: 1205905 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261834 RingCT/type: yes/0
Extra: 01fc17684762d16e2b03f06eec8ab97d200aeae85add28a3d816697c83dca1ae490211000000242609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b67890c5be78d6ca11542a908e0bd3eef360641379ee3f8196466db251c8a613 0.600000000000 1692604 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": 1205915, "vin": [ { "gen": { "height": 1205905 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b67890c5be78d6ca11542a908e0bd3eef360641379ee3f8196466db251c8a613" } } ], "extra": [ 1, 252, 23, 104, 71, 98, 209, 110, 43, 3, 240, 110, 236, 138, 185, 125, 32, 10, 234, 232, 90, 221, 40, 163, 216, 22, 105, 124, 131, 220, 161, 174, 73, 2, 17, 0, 0, 0, 36, 38, 9, 179, 160, 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