Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d20e04373d9d276c0fe7e523773d93cb567120b09c44bc2027da86da964b540

Tx prefix hash: d3abced39fbf7dcb5c06dcfc75a7a875b4539c59ecdd53f61c40c0842d9cc172
Tx public key: 82040456dff4af7e655d07a08c2ba05d90e141b0d3c6469e97cc241bf7d6af94
Timestamp: 1734706337 Timestamp [UCT]: 2024-12-20 14:52:17 Age [y:d:h:m:s]: 00:089:08:34:53
Block: 1179391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63642 RingCT/type: yes/0
Extra: 0182040456dff4af7e655d07a08c2ba05d90e141b0d3c6469e97cc241bf7d6af9402110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c890a0082f900300bde2ca0828a83b23a92c716ace4ee1bfb7735072036e7d0 0.600000000000 1665786 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": 1179401, "vin": [ { "gen": { "height": 1179391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c890a0082f900300bde2ca0828a83b23a92c716ace4ee1bfb7735072036e7d0" } } ], "extra": [ 1, 130, 4, 4, 86, 223, 244, 175, 126, 101, 93, 7, 160, 140, 43, 160, 93, 144, 225, 65, 176, 211, 198, 70, 158, 151, 204, 36, 27, 247, 214, 175, 148, 2, 17, 0, 0, 0, 11, 31, 10, 83, 235, 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