Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 412b6b4a9a5ac0200963924f98f171b7a6cc44afb9e07763bc6c450ea4ad8146

Tx prefix hash: fb26f20dbc7026e62aa9c46b2da59e188aae73c13f64ce87244b2d56de6df5ff
Tx public key: dedb38bae8c9d272e104412f5a188ee33ecdff06156b4853c44f0fe84ce99486
Timestamp: 1755701613 Timestamp [UCT]: 2025-08-20 14:53:33 Age [y:d:h:m:s]: 00:165:23:45:01
Block: 1350646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118467 RingCT/type: yes/0
Extra: 01dedb38bae8c9d272e104412f5a188ee33ecdff06156b4853c44f0fe84ce99486021100000003b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3967997ec59d8c420d4f46bae30e0f1884d3fffdfc4a965df20e6e7421b033fc 0.600000000000 1838591 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": 1350656, "vin": [ { "gen": { "height": 1350646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3967997ec59d8c420d4f46bae30e0f1884d3fffdfc4a965df20e6e7421b033fc" } } ], "extra": [ 1, 222, 219, 56, 186, 232, 201, 210, 114, 225, 4, 65, 47, 90, 24, 142, 227, 62, 205, 255, 6, 21, 107, 72, 83, 196, 79, 15, 232, 76, 233, 148, 134, 2, 17, 0, 0, 0, 3, 178, 247, 132, 196, 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