Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15f74853bdf56ccea882efb783d54ca71b8027eb312cf093061006383b39a9e1

Tx prefix hash: 356a287d8ceff6ba2382aefe70031582def2fc70568cab0b75d4fcdce6ff0f2b
Tx public key: e35188f9ad84eb8f479b24c831f5202ac8ce210aa1d83dda4eb6d65d49a214a0
Timestamp: 1735348965 Timestamp [UCT]: 2024-12-28 01:22:45 Age [y:d:h:m:s]: 00:081:22:04:25
Block: 1184667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58365 RingCT/type: yes/0
Extra: 01e35188f9ad84eb8f479b24c831f5202ac8ce210aa1d83dda4eb6d65d49a214a00211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43d62f304b7655d64447b86be1abef85b7b1b1e98d4dc07e9f9ffa84ce82a4e9 0.600000000000 1671126 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": 1184677, "vin": [ { "gen": { "height": 1184667 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43d62f304b7655d64447b86be1abef85b7b1b1e98d4dc07e9f9ffa84ce82a4e9" } } ], "extra": [ 1, 227, 81, 136, 249, 173, 132, 235, 143, 71, 155, 36, 200, 49, 245, 32, 42, 200, 206, 33, 10, 161, 216, 61, 218, 78, 182, 214, 93, 73, 162, 20, 160, 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