Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53ffb03bd6687aa1e25df6f54b99dc77c42d9f86c0c3429db9439f14c6b3d6af

Tx prefix hash: ffd42097e569bdd790f601cde3f5bb626ef2f0a58b9a35ee4996779965227339
Tx public key: 739defd76e703737d7d7e8b7949f3cbb6ee031a7a503562e8556d43ed1449996
Timestamp: 1704193320 Timestamp [UCT]: 2024-01-02 11:02:00 Age [y:d:h:m:s]: 01:119:12:27:06
Block: 926499 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346546 RingCT/type: yes/0
Extra: 01739defd76e703737d7d7e8b7949f3cbb6ee031a7a503562e8556d43ed144999602110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0022d34df385537e3f3d8aca3b21117dfd7dcab525319cc5bd999903ee697ec3 0.600000000000 1384285 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": 926509, "vin": [ { "gen": { "height": 926499 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0022d34df385537e3f3d8aca3b21117dfd7dcab525319cc5bd999903ee697ec3" } } ], "extra": [ 1, 115, 157, 239, 215, 110, 112, 55, 55, 215, 215, 232, 183, 148, 159, 60, 187, 110, 224, 49, 167, 165, 3, 86, 46, 133, 86, 212, 62, 209, 68, 153, 150, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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