Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3855efa2ae1559ee8615b6379f3859c71487713e42d6b85c2dc41e511cd4ffb

Tx prefix hash: c31823a9ee9fa65ff1f49765812ebaf9d38c0722655de3e21ba76192297fe068
Tx public key: 8992a9dd6725d1af0b19cf0d57cb783669d8e6a64404b2fd4bcedecdcfaf84f8
Timestamp: 1715449662 Timestamp [UCT]: 2024-05-11 17:47:42 Age [y:d:h:m:s]: 00:187:05:42:03
Block: 1019860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134000 RingCT/type: yes/0
Extra: 018992a9dd6725d1af0b19cf0d57cb783669d8e6a64404b2fd4bcedecdcfaf84f802110000000341ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16ae5392e57fd6f1ca15d4dca43bd277607f943b9770671034e4a1838558fd43 0.600000000000 1483913 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": 1019870, "vin": [ { "gen": { "height": 1019860 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16ae5392e57fd6f1ca15d4dca43bd277607f943b9770671034e4a1838558fd43" } } ], "extra": [ 1, 137, 146, 169, 221, 103, 37, 209, 175, 11, 25, 207, 13, 87, 203, 120, 54, 105, 216, 230, 166, 68, 4, 178, 253, 75, 206, 222, 205, 207, 175, 132, 248, 2, 17, 0, 0, 0, 3, 65, 238, 28, 155, 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