Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35356aecb83c10e1942b9412276557f5ef7ce7a4afe6bf497c0b58cee6925781

Tx prefix hash: 5f3cbe7e12bc4ae9bae818a5a2a9394bd9983053fb5aaab53a3cc8a8ba440859
Tx public key: 892aa7cfa48b5d956b74304bcb2aa0311591879d41268ee934ca8fa9ff3535c9
Timestamp: 1763498366 Timestamp [UCT]: 2025-11-18 20:39:26 Age [y:d:h:m:s]: 00:009:09:49:16
Block: 1415048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6741 RingCT/type: yes/0
Extra: 01892aa7cfa48b5d956b74304bcb2aa0311591879d41268ee934ca8fa9ff3535c9021100000003fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e1f64fa5e20dfa7eaf0eecafc2faa6dc2302870e15acc3735352f232f8db2b3 0.600000000000 1903541 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": 1415058, "vin": [ { "gen": { "height": 1415048 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e1f64fa5e20dfa7eaf0eecafc2faa6dc2302870e15acc3735352f232f8db2b3" } } ], "extra": [ 1, 137, 42, 167, 207, 164, 139, 93, 149, 107, 116, 48, 75, 203, 42, 160, 49, 21, 145, 135, 157, 65, 38, 142, 233, 52, 202, 143, 169, 255, 53, 53, 201, 2, 17, 0, 0, 0, 3, 251, 143, 208, 137, 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