Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25c706acd147b9cbc00d4163d39e5454cd0247a2c75ecbbfa484dc32dc26781c

Tx prefix hash: 36747e699037e876388f7cb68fe7f383b1ec2d14d79045c0458991b216910d53
Tx public key: a090b4584315c113b429a47a90c495b5c328ce9dfca58c83dcd0c4ee503e3132
Timestamp: 1734219643 Timestamp [UCT]: 2024-12-14 23:40:43 Age [y:d:h:m:s]: 00:094:22:37:28
Block: 1175355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67643 RingCT/type: yes/0
Extra: 01a090b4584315c113b429a47a90c495b5c328ce9dfca58c83dcd0c4ee503e3132021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04e991a77ec95b3a803ab02fe8dbb097df5e29f44c8858504d7ddd64bf636738 0.600000000000 1661626 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": 1175365, "vin": [ { "gen": { "height": 1175355 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04e991a77ec95b3a803ab02fe8dbb097df5e29f44c8858504d7ddd64bf636738" } } ], "extra": [ 1, 160, 144, 180, 88, 67, 21, 193, 19, 180, 41, 164, 122, 144, 196, 149, 181, 195, 40, 206, 157, 252, 165, 140, 131, 220, 208, 196, 238, 80, 62, 49, 50, 2, 17, 0, 0, 0, 7, 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