Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab30a20720c3e5597f0ebbda3a48a6e6cb7fd6f30f2fdd97f3f488f6363fb37e

Tx prefix hash: af5c248a8956be615f0a9b7b5136c4e6e2cce5fcd43178412b904159cf2f64b0
Tx public key: e586037945c7166cedd3f89d98971161299ae5fee315066a01b2c253ef32ecf9
Timestamp: 1726123974 Timestamp [UCT]: 2024-09-12 06:52:54 Age [y:d:h:m:s]: 00:101:11:27:39
Block: 1108316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72607 RingCT/type: yes/0
Extra: 01e586037945c7166cedd3f89d98971161299ae5fee315066a01b2c253ef32ecf902110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7cf6fb153b631de5490233f45feb74b004bfb073e10ce04a29ed5139ec07d8f8 0.600000000000 1586171 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": 1108326, "vin": [ { "gen": { "height": 1108316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7cf6fb153b631de5490233f45feb74b004bfb073e10ce04a29ed5139ec07d8f8" } } ], "extra": [ 1, 229, 134, 3, 121, 69, 199, 22, 108, 237, 211, 248, 157, 152, 151, 17, 97, 41, 154, 229, 254, 227, 21, 6, 106, 1, 178, 194, 83, 239, 50, 236, 249, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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