Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 540b31ec6ec381b1b172dfe663bc80f796d0cbc9d4f2f264c86e914ea2b9429f

Tx prefix hash: fc0f37f657aae303ad068e2ec04788b97a2b1483ff505ae278a086571f137c3d
Tx public key: bd4f69e31a6f81a522460fcbafe009867f4517f8da055ff0fd7a48096699f11c
Timestamp: 1679901180 Timestamp [UCT]: 2023-03-27 07:13:00 Age [y:d:h:m:s]: 02:060:17:24:05
Block: 726016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 564963 RingCT/type: yes/0
Extra: 01bd4f69e31a6f81a522460fcbafe009867f4517f8da055ff0fd7a48096699f11c02110000000175e3f0e9000000000000000000

1 output(s) for total of 2.412169638000 dcy

stealth address amount amount idx
00: 2d762627397342fb7a265a77e230da0f6847fa824df4f818f5fc14be56c051f8 2.412169638000 1171233 of 0

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": 726026, "vin": [ { "gen": { "height": 726016 } } ], "vout": [ { "amount": 2412169638, "target": { "key": "2d762627397342fb7a265a77e230da0f6847fa824df4f818f5fc14be56c051f8" } } ], "extra": [ 1, 189, 79, 105, 227, 26, 111, 129, 165, 34, 70, 15, 203, 175, 224, 9, 134, 127, 69, 23, 248, 218, 5, 95, 240, 253, 122, 72, 9, 102, 153, 241, 28, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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