Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c3d224c1c53777c497c0d455eecc8fe9272946cc63b953819462b78ca4f72fc

Tx prefix hash: 2e73a1fd9b4c35b979f6bd2f802a4bfa9747917f740e8f318648b9fa91f4f211
Tx public key: 299fa64776b05779e4e0fe10d6d83d5bf987f0b6aaff2555a1bd2343e365ddd5
Timestamp: 1740128416 Timestamp [UCT]: 2025-02-21 09:00:16 Age [y:d:h:m:s]: 00:345:10:03:38
Block: 1223963 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244566 RingCT/type: yes/0
Extra: 01299fa64776b05779e4e0fe10d6d83d5bf987f0b6aaff2555a1bd2343e365ddd502110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f52b754db16292a4cc513b6021a84dc0d6c8c241013a2a08669888b8388eed82 0.600000000000 1710820 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": 1223973, "vin": [ { "gen": { "height": 1223963 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f52b754db16292a4cc513b6021a84dc0d6c8c241013a2a08669888b8388eed82" } } ], "extra": [ 1, 41, 159, 166, 71, 118, 176, 87, 121, 228, 224, 254, 16, 214, 216, 61, 91, 249, 135, 240, 182, 170, 255, 37, 85, 161, 189, 35, 67, 227, 101, 221, 213, 2, 17, 0, 0, 0, 12, 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