Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ddd3d52891a80d4d02c4bc833307dc4f2a6eb66ffd8770b5f0ecd4e52a58b26

Tx prefix hash: d07d1cd0831d596da64d4f1bfce913882585bab949fec1cfc2715e06f302db62
Tx public key: 512985e431c40b7e4a495dc42a6b431eb0b339ebd51f6dded1963b291d63dd2c
Timestamp: 1753128605 Timestamp [UCT]: 2025-07-21 20:10:05 Age [y:d:h:m:s]: 00:123:07:07:45
Block: 1330460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86933 RingCT/type: yes/0
Extra: 01512985e431c40b7e4a495dc42a6b431eb0b339ebd51f6dded1963b291d63dd2c02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 320e6de58654a514fe01a5a29e2682a376a4f8fe5a9e7d903c0af4f762715015 0.600000000000 1818251 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": 1330470, "vin": [ { "gen": { "height": 1330460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "320e6de58654a514fe01a5a29e2682a376a4f8fe5a9e7d903c0af4f762715015" } } ], "extra": [ 1, 81, 41, 133, 228, 49, 196, 11, 126, 74, 73, 93, 196, 42, 107, 67, 30, 176, 179, 57, 235, 213, 31, 109, 222, 209, 150, 59, 41, 29, 99, 221, 44, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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