Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1251d31b7984b6b86eba0809882c0d1c253300fe47f4907608a915525c1d737

Tx prefix hash: 23a926025f04dd3897d051b63b250ae6df6a115acc9ca5ccd81a2820c723fcbb
Tx public key: de9309e5bac023a20521f8f054943a3a4ad66b857d132d2cf4dfd38ac9455224
Timestamp: 1729703942 Timestamp [UCT]: 2024-10-23 17:19:02 Age [y:d:h:m:s]: 00:140:18:01:06
Block: 1137973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100400 RingCT/type: yes/0
Extra: 01de9309e5bac023a20521f8f054943a3a4ad66b857d132d2cf4dfd38ac94552240211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 109901c1d996e098b43e1cc034fb767b5727e7a0bfba72e3a0d29f4090fd3ed5 0.600000000000 1621566 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": 1137983, "vin": [ { "gen": { "height": 1137973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "109901c1d996e098b43e1cc034fb767b5727e7a0bfba72e3a0d29f4090fd3ed5" } } ], "extra": [ 1, 222, 147, 9, 229, 186, 192, 35, 162, 5, 33, 248, 240, 84, 148, 58, 58, 74, 214, 107, 133, 125, 19, 45, 44, 244, 223, 211, 138, 201, 69, 82, 36, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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