Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d78665b3d616a4f6440a13e14e81a26093e4a1970fa38f587fac5ede1132c06d

Tx prefix hash: 878ce06002d1ac006346599160804ed34cbf2ba324f9f4c3b4aa3e139bea6f0c
Tx public key: 4755b670a0ae5c881f858c0da028dbd030b6598d6658a60881d85f93eb1b3140
Timestamp: 1696291562 Timestamp [UCT]: 2023-10-03 00:06:02 Age [y:d:h:m:s]: 01:185:23:46:48
Block: 861204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393973 RingCT/type: yes/0
Extra: 014755b670a0ae5c881f858c0da028dbd030b6598d6658a60881d85f93eb1b3140021100000006faf35c9c000000000000000000

1 output(s) for total of 0.859950960000 dcy

stealth address amount amount idx
00: 5ac1ade5f94cecca8314c45d9d556181ac4f69e8fb43d46355cb61638d20e081 0.859950960000 1315534 of 0

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": 861214, "vin": [ { "gen": { "height": 861204 } } ], "vout": [ { "amount": 859950960, "target": { "key": "5ac1ade5f94cecca8314c45d9d556181ac4f69e8fb43d46355cb61638d20e081" } } ], "extra": [ 1, 71, 85, 182, 112, 160, 174, 92, 136, 31, 133, 140, 13, 160, 40, 219, 208, 48, 182, 89, 141, 102, 88, 166, 8, 129, 216, 95, 147, 235, 27, 49, 64, 2, 17, 0, 0, 0, 6, 250, 243, 92, 156, 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