Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 555b273dc97edeb746a51e2852353c954195df8d572003b24cf5265de73f07c0

Tx prefix hash: d04b4b2f154c4c113b2f8968c23c577991a15c65138143000df32b0d2f82a9d8
Tx public key: d5199913a9a521f1c60670aef604d88a77cfabe30f4aedfa046694f8f1ddde24
Timestamp: 1713194232 Timestamp [UCT]: 2024-04-15 15:17:12 Age [y:d:h:m:s]: 01:036:14:56:44
Block: 1001122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287156 RingCT/type: yes/0
Extra: 01d5199913a9a521f1c60670aef604d88a77cfabe30f4aedfa046694f8f1ddde240211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8fb9e99cfd1d71c7f7747f41e41c693f2ae3883668d1365712b927ea21408651 0.600000000000 1461624 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": 1001132, "vin": [ { "gen": { "height": 1001122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8fb9e99cfd1d71c7f7747f41e41c693f2ae3883668d1365712b927ea21408651" } } ], "extra": [ 1, 213, 25, 153, 19, 169, 165, 33, 241, 198, 6, 112, 174, 246, 4, 216, 138, 119, 207, 171, 227, 15, 74, 237, 250, 4, 102, 148, 248, 241, 221, 222, 36, 2, 17, 0, 0, 0, 1, 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