Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9d0f898264497f6e037e8a6baa77fc8a72b84ade0b3821051347ce70e9a4e6c

Tx prefix hash: 4afd6740511ae5b4913931e2d6b73d2ae4babf611f025ef0669bba78c29ceca0
Tx public key: 6a3e8eda2e03ba5e5f9386fcd59786496ce1e9674b92a1e738ebbd9e9c6b3836
Timestamp: 1704058949 Timestamp [UCT]: 2023-12-31 21:42:29 Age [y:d:h:m:s]: 01:312:09:03:56
Block: 925388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 482086 RingCT/type: yes/0
Extra: 016a3e8eda2e03ba5e5f9386fcd59786496ce1e9674b92a1e738ebbd9e9c6b383602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7114960a3cffd212ebb2435afa72fe77a1be5d365eb670035a22e5dd7ba33d9b 0.600000000000 1383150 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": 925398, "vin": [ { "gen": { "height": 925388 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7114960a3cffd212ebb2435afa72fe77a1be5d365eb670035a22e5dd7ba33d9b" } } ], "extra": [ 1, 106, 62, 142, 218, 46, 3, 186, 94, 95, 147, 134, 252, 213, 151, 134, 73, 108, 225, 233, 103, 75, 146, 161, 231, 56, 235, 189, 158, 156, 107, 56, 54, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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