Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13a8e1d0e9728171642315519a0851650cc9a109860a1e446acd3d0be05ea4c7

Tx prefix hash: ec877fca4bc1dc3a6984dc81e0111815c7322f1c8a89c1d8c642d7e62b67e677
Tx public key: 4c327fa57b56ef0f2ab6e59bcd1a34a0739bebc29e185de0a4e0ec62351671ca
Timestamp: 1734831688 Timestamp [UCT]: 2024-12-22 01:41:28 Age [y:d:h:m:s]: 00:024:06:25:01
Block: 1180428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17322 RingCT/type: yes/0
Extra: 014c327fa57b56ef0f2ab6e59bcd1a34a0739bebc29e185de0a4e0ec62351671ca021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e4a46273008f455a0f7c409ddc543ea547312b01f1d1946f148633d677d9cf8 0.600000000000 1666839 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": 1180438, "vin": [ { "gen": { "height": 1180428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e4a46273008f455a0f7c409ddc543ea547312b01f1d1946f148633d677d9cf8" } } ], "extra": [ 1, 76, 50, 127, 165, 123, 86, 239, 15, 42, 182, 229, 155, 205, 26, 52, 160, 115, 155, 235, 194, 158, 24, 93, 224, 164, 224, 236, 98, 53, 22, 113, 202, 2, 17, 0, 0, 0, 2, 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