Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 557ce52f576f41a19a28c7db6dc216c2b866e4ba20ea47a4b57e381a2514346b

Tx prefix hash: 4f0f1ebc7f7c810730daba396043efd4e717f1e2d8c688f0d5a00e789e81a086
Tx public key: eafadc30c6e132bb246bd23dbd1f2d27f65da30858b78f9d690c41aa193b1b2e
Timestamp: 1736518697 Timestamp [UCT]: 2025-01-10 14:18:17 Age [y:d:h:m:s]: 00:158:12:11:26
Block: 1194361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112995 RingCT/type: yes/0
Extra: 01eafadc30c6e132bb246bd23dbd1f2d27f65da30858b78f9d690c41aa193b1b2e021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 950ff6f2b4605ccdfdafdc434beea94c4614fbf07fd0f80c7310ad0d8b3e225d 0.600000000000 1680930 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": 1194371, "vin": [ { "gen": { "height": 1194361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "950ff6f2b4605ccdfdafdc434beea94c4614fbf07fd0f80c7310ad0d8b3e225d" } } ], "extra": [ 1, 234, 250, 220, 48, 198, 225, 50, 187, 36, 107, 210, 61, 189, 31, 45, 39, 246, 93, 163, 8, 88, 183, 143, 157, 105, 12, 65, 170, 25, 59, 27, 46, 2, 17, 0, 0, 0, 1, 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