Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b46f08b68bda2dd71855fef0affcc5ed100355a78d0cb6333a60160db14c47a

Tx prefix hash: 5374770681e780c2cd9e6320720a98b6a825d6da3c8be19030c5badf7da56e8b
Tx public key: 8f2a676de1e37343c48b82bff3ec6940214a32824eaffe8128194a3512c1755e
Timestamp: 1708921769 Timestamp [UCT]: 2024-02-26 04:29:29 Age [y:d:h:m:s]: 01:079:12:17:59
Block: 965718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317858 RingCT/type: yes/0
Extra: 018f2a676de1e37343c48b82bff3ec6940214a32824eaffe8128194a3512c1755e0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7d007072ce20396d45cf4cf654db1cb5612db54712112f8d8ffd2f42b8f477d 0.600000000000 1425473 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": 965728, "vin": [ { "gen": { "height": 965718 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7d007072ce20396d45cf4cf654db1cb5612db54712112f8d8ffd2f42b8f477d" } } ], "extra": [ 1, 143, 42, 103, 109, 225, 227, 115, 67, 196, 139, 130, 191, 243, 236, 105, 64, 33, 74, 50, 130, 78, 175, 254, 129, 40, 25, 74, 53, 18, 193, 117, 94, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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