Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 033d3def5c5c834b7cbe27b02eeb0ba0b3dd10786ec188b5b13df9e44eef1e2d

Tx prefix hash: ea455c8e2d1a1a2ab500212a9c812e4130dbd2f1d17f0b22b81c6f9f693a33e8
Tx public key: 19c8eb7855eec52b4679a9abe59405f0cf7130d08acdf77c7bdd06e19c7f2a83
Timestamp: 1740786864 Timestamp [UCT]: 2025-02-28 23:54:24 Age [y:d:h:m:s]: 00:332:22:38:18
Block: 1229424 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235622 RingCT/type: yes/0
Extra: 0119c8eb7855eec52b4679a9abe59405f0cf7130d08acdf77c7bdd06e19c7f2a8302110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25b6b949d4e0b082e32fa32e12d4345fce04e8e9e5ab3bf1285a5cbeada7e50b 0.600000000000 1716311 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": 1229434, "vin": [ { "gen": { "height": 1229424 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25b6b949d4e0b082e32fa32e12d4345fce04e8e9e5ab3bf1285a5cbeada7e50b" } } ], "extra": [ 1, 25, 200, 235, 120, 85, 238, 197, 43, 70, 121, 169, 171, 229, 148, 5, 240, 207, 113, 48, 208, 138, 205, 247, 124, 123, 221, 6, 225, 156, 127, 42, 131, 2, 17, 0, 0, 0, 12, 0, 127, 151, 138, 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