Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82c9a383cd94b80f9b2f16830c4635e6ac7f63553c6c8b4f3ac0337b5913f95d

Tx prefix hash: 2443836110c6bb7d08a19cf2640980e5b40a35133e397630e7fd444b85c642e3
Tx public key: 9ceebccc53a9e856c075cf3cf2e82415658fcc810c2b563b8708ebe0d230c142
Timestamp: 1724552162 Timestamp [UCT]: 2024-08-25 02:16:02 Age [y:d:h:m:s]: 00:230:16:15:03
Block: 1095320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164702 RingCT/type: yes/0
Extra: 019ceebccc53a9e856c075cf3cf2e82415658fcc810c2b563b8708ebe0d230c142021100000001e337358e000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7c9a8581538175d422ef5be69c853668d9abd78eda3c1094badebea06d8c6c5 0.600000000000 1570481 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": 1095330, "vin": [ { "gen": { "height": 1095320 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7c9a8581538175d422ef5be69c853668d9abd78eda3c1094badebea06d8c6c5" } } ], "extra": [ 1, 156, 238, 188, 204, 83, 169, 232, 86, 192, 117, 207, 60, 242, 232, 36, 21, 101, 143, 204, 129, 12, 43, 86, 59, 135, 8, 235, 224, 210, 48, 193, 66, 2, 17, 0, 0, 0, 1, 227, 55, 53, 142, 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