Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35ca8a615345022c27794bc54326b819538a9d2b344a31b45e79d20248d83212

Tx prefix hash: d22ef592d23b0aee0b2a06095e72765283855a3b1fe9dccae354c4282abcebb1
Tx public key: e7bc3f75da7477d536d83d486e063460e38c2f5a7c8d1afb7ce70b9bee7acb40
Timestamp: 1759734084 Timestamp [UCT]: 2025-10-06 07:01:24 Age [y:d:h:m:s]: 00:038:21:44:34
Block: 1383852 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27860 RingCT/type: yes/0
Extra: 01e7bc3f75da7477d536d83d486e063460e38c2f5a7c8d1afb7ce70b9bee7acb40021100000006a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31094f4e6bcbed5cc11b0760df3f61768e5d5485479c097d65c2a1763b019a02 0.600000000000 1872001 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": 1383862, "vin": [ { "gen": { "height": 1383852 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31094f4e6bcbed5cc11b0760df3f61768e5d5485479c097d65c2a1763b019a02" } } ], "extra": [ 1, 231, 188, 63, 117, 218, 116, 119, 213, 54, 216, 61, 72, 110, 6, 52, 96, 227, 140, 47, 90, 124, 141, 26, 251, 124, 231, 11, 155, 238, 122, 203, 64, 2, 17, 0, 0, 0, 6, 165, 220, 205, 121, 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