Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1f3cc821496437e0c0fef7fd3441e22e622bb731f8331c542f51196abfe9dac

Tx prefix hash: 9803fdbae902e6db444f72aa7c119dbaaae48ed878b31a196dd507a3ccae9445
Tx public key: 5bdb5d6ae8c8e1d7ad452959e41339856c26309af5a269721f007cbc69b0e867
Timestamp: 1763622298 Timestamp [UCT]: 2025-11-20 07:04:58 Age [y:d:h:m:s]: 00:007:23:29:50
Block: 1416073 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5718 RingCT/type: yes/0
Extra: 015bdb5d6ae8c8e1d7ad452959e41339856c26309af5a269721f007cbc69b0e8670211000000037b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b1c81901e8523fb06bf8c53704a2a9abdfcf3b54f372b4bcf9643aec0fcfc31 0.600000000000 1904592 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": 1416083, "vin": [ { "gen": { "height": 1416073 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b1c81901e8523fb06bf8c53704a2a9abdfcf3b54f372b4bcf9643aec0fcfc31" } } ], "extra": [ 1, 91, 219, 93, 106, 232, 200, 225, 215, 173, 69, 41, 89, 228, 19, 57, 133, 108, 38, 48, 154, 245, 162, 105, 114, 31, 0, 124, 188, 105, 176, 232, 103, 2, 17, 0, 0, 0, 3, 123, 30, 81, 172, 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