Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87c0ced845f0a5670bb02866e714c5f1f906f706254f1eb8637e564e8b3fe3e7

Tx prefix hash: af0e982798ef985ee2d0eb401fc39af78dad722789b28d99101b40721cb1431f
Tx public key: ff009c2dfcc9fc1e38e8fda3856f0bb4074d6d51d791ced4bf9534aa90bb3b8c
Timestamp: 1731816119 Timestamp [UCT]: 2024-11-17 04:01:59 Age [y:d:h:m:s]: 00:362:10:58:45
Block: 1155417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256603 RingCT/type: yes/0
Extra: 01ff009c2dfcc9fc1e38e8fda3856f0bb4074d6d51d791ced4bf9534aa90bb3b8c021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81d70c1727e3fd02b1e1110829aab5101b6a780248889c1427c58a9321ee9d75 0.600000000000 1641032 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": 1155427, "vin": [ { "gen": { "height": 1155417 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81d70c1727e3fd02b1e1110829aab5101b6a780248889c1427c58a9321ee9d75" } } ], "extra": [ 1, 255, 0, 156, 45, 252, 201, 252, 30, 56, 232, 253, 163, 133, 111, 11, 180, 7, 77, 109, 81, 215, 145, 206, 212, 191, 149, 52, 170, 144, 187, 59, 140, 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