Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e9c3d9564dc274fcdb09346be40bb81e953ea58a770eefaeb5f47a7bc32d2f5

Tx prefix hash: 75589b5afcad530770f4362bb8e0c9ae0f72b057dd1eb9e4e4876d17b87a0ea1
Tx public key: 0c9babc3c77418ed66870ed8d7ac2535a8e8bc135273bb462e8b5ef6986933d5
Timestamp: 1736985478 Timestamp [UCT]: 2025-01-15 23:57:58 Age [y:d:h:m:s]: 00:304:04:33:07
Block: 1198223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214916 RingCT/type: yes/0
Extra: 010c9babc3c77418ed66870ed8d7ac2535a8e8bc135273bb462e8b5ef6986933d50211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52d638059c5ebfd5799c837e5b4e1504e041262e8549adc6ce6fe25f3f256145 0.600000000000 1684842 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": 1198233, "vin": [ { "gen": { "height": 1198223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52d638059c5ebfd5799c837e5b4e1504e041262e8549adc6ce6fe25f3f256145" } } ], "extra": [ 1, 12, 155, 171, 195, 199, 116, 24, 237, 102, 135, 14, 216, 215, 172, 37, 53, 168, 232, 188, 19, 82, 115, 187, 70, 46, 139, 94, 246, 152, 105, 51, 213, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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