Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb129a2936e036068804c634858e0f32b8b9961b2d0041367b79e746b960fb5b

Tx prefix hash: 2285d50eecc7b26ef8d811b9c1a87db2a581f6267abde126f8cf985760087236
Tx public key: af0e93d03a2262bd6dee6cc614a4deb9445481333e8c86d0e1640b8bcd26dac9
Timestamp: 1705394669 Timestamp [UCT]: 2024-01-16 08:44:29 Age [y:d:h:m:s]: 01:077:07:45:30
Block: 936450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316361 RingCT/type: yes/0
Extra: 01af0e93d03a2262bd6dee6cc614a4deb9445481333e8c86d0e1640b8bcd26dac902110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfa17c36c9d2cbe21dd30e1fc8e2c438382e3a04f53c8971294f719decd56a21 0.600000000000 1394476 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": 936460, "vin": [ { "gen": { "height": 936450 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfa17c36c9d2cbe21dd30e1fc8e2c438382e3a04f53c8971294f719decd56a21" } } ], "extra": [ 1, 175, 14, 147, 208, 58, 34, 98, 189, 109, 238, 108, 198, 20, 164, 222, 185, 68, 84, 129, 51, 62, 140, 134, 208, 225, 100, 11, 139, 205, 38, 218, 201, 2, 17, 0, 0, 0, 11, 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