Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad4d4cbc245a273ea2c45cd29055cb39f7e370cb120d4101427c9a18558f8ba1

Tx prefix hash: a7b039a0a15791de9aa4ddc32ab59fbad07173cdf0a6cbff04cc3fb4527c8872
Tx public key: f126af9abf21c9d99ce5f4117e791a3f5bad4628bb5df3c15dc8bf04d78aa522
Timestamp: 1737680994 Timestamp [UCT]: 2025-01-24 01:09:54 Age [y:d:h:m:s]: 00:332:09:46:34
Block: 1203947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235153 RingCT/type: yes/0
Extra: 01f126af9abf21c9d99ce5f4117e791a3f5bad4628bb5df3c15dc8bf04d78aa522021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ecd4d750ccc0d3d48c775215e24d8a9ea6a37d2de8bf64e6a15919fb6021b8cb 0.600000000000 1690628 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": 1203957, "vin": [ { "gen": { "height": 1203947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ecd4d750ccc0d3d48c775215e24d8a9ea6a37d2de8bf64e6a15919fb6021b8cb" } } ], "extra": [ 1, 241, 38, 175, 154, 191, 33, 201, 217, 156, 229, 244, 17, 126, 121, 26, 63, 91, 173, 70, 40, 187, 93, 243, 193, 93, 200, 191, 4, 215, 138, 165, 34, 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