Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d12ec733256744612077e044979f82fe56e4749f9a931d885acdfc72e4424ffd

Tx prefix hash: 870d5de227c8f11ed406f7da588e212a5a5b2339f1a21156c2bc76e91b07b1f3
Tx public key: ddd7d4502a9eada9d8b20fbd96301b9f31e186875876481e591c1141f6b874c2
Timestamp: 1762558070 Timestamp [UCT]: 2025-11-07 23:27:50 Age [y:d:h:m:s]: 00:045:22:54:21
Block: 1407259 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32896 RingCT/type: yes/0
Extra: 01ddd7d4502a9eada9d8b20fbd96301b9f31e186875876481e591c1141f6b874c202110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f81b5ee473ae46e0a32c3d3f33f81e1eaa7d7495bbfa139191c3f360297ffb2 0.600000000000 1895678 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": 1407269, "vin": [ { "gen": { "height": 1407259 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f81b5ee473ae46e0a32c3d3f33f81e1eaa7d7495bbfa139191c3f360297ffb2" } } ], "extra": [ 1, 221, 215, 212, 80, 42, 158, 173, 169, 216, 178, 15, 189, 150, 48, 27, 159, 49, 225, 134, 135, 88, 118, 72, 30, 89, 28, 17, 65, 246, 184, 116, 194, 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