Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 867ded46fcbe35647a3b1388526558f4bbafcba64c838a0dd0c5d24f01d78fb4

Tx prefix hash: 370a4c82d68255fad4a52631a2ea55ae8a18d73d99160b6cac406c65c10ad12a
Tx public key: 2116f55062fc7665c5e711c1e47f35b460c68f3d294a7b9cc1e7609f92102d0b
Timestamp: 1745268681 Timestamp [UCT]: 2025-04-21 20:51:21 Age [y:d:h:m:s]: 00:213:11:56:24
Block: 1266533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150295 RingCT/type: yes/0
Extra: 012116f55062fc7665c5e711c1e47f35b460c68f3d294a7b9cc1e7609f92102d0b02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d0a837048e253b825a954cbdb787cc5a0c6740f9e5130a34ffea0dddd970368 0.600000000000 1753754 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": 1266543, "vin": [ { "gen": { "height": 1266533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d0a837048e253b825a954cbdb787cc5a0c6740f9e5130a34ffea0dddd970368" } } ], "extra": [ 1, 33, 22, 245, 80, 98, 252, 118, 101, 197, 231, 17, 193, 228, 127, 53, 180, 96, 198, 143, 61, 41, 74, 123, 156, 193, 231, 96, 159, 146, 16, 45, 11, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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