Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbed04ad2604bc0e8945fdfe94f3371e815292e7f58e8bbaecd7201aa3072209

Tx prefix hash: edd12818005d309a9720d9353d077b112de6d55b10f3398480226ebf4bf1d16c
Tx public key: cf819e31e67f713dc9c61cfa106b4cf3b4a18eb9560f73d9ec6a3f294f50bf3b
Timestamp: 1735263682 Timestamp [UCT]: 2024-12-27 01:41:22 Age [y:d:h:m:s]: 00:097:01:54:34
Block: 1183971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69160 RingCT/type: yes/0
Extra: 01cf819e31e67f713dc9c61cfa106b4cf3b4a18eb9560f73d9ec6a3f294f50bf3b021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d6deaad7510d2d62b51fe0584e755a1bebe5651bd47e14fab1104a929146eb5 0.600000000000 1670422 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": 1183981, "vin": [ { "gen": { "height": 1183971 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d6deaad7510d2d62b51fe0584e755a1bebe5651bd47e14fab1104a929146eb5" } } ], "extra": [ 1, 207, 129, 158, 49, 230, 127, 113, 61, 201, 198, 28, 250, 16, 107, 76, 243, 180, 161, 142, 185, 86, 15, 115, 217, 236, 106, 63, 41, 79, 80, 191, 59, 2, 17, 0, 0, 0, 4, 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