Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a901968b30e91771889244360e00e31dc9ad67ba015423131692730613d8f5da

Tx prefix hash: 038d40768fa9030e95e716408458367623a797cc93e0c83e5c4769bf86a603b1
Tx public key: 1b1417c8f592c4eb94c1f1cbd9e8079c3f5ec8c25b6eadf82a0386a72faf573f
Timestamp: 1703776946 Timestamp [UCT]: 2023-12-28 15:22:26 Age [y:d:h:m:s]: 01:010:19:47:06
Block: 923054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269068 RingCT/type: yes/0
Extra: 011b1417c8f592c4eb94c1f1cbd9e8079c3f5ec8c25b6eadf82a0386a72faf573f0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02c1c2583c873e341d6c6c234bcc84ced9018784d3038ab8e867e13fd90f68e1 0.600000000000 1380770 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": 923064, "vin": [ { "gen": { "height": 923054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02c1c2583c873e341d6c6c234bcc84ced9018784d3038ab8e867e13fd90f68e1" } } ], "extra": [ 1, 27, 20, 23, 200, 245, 146, 196, 235, 148, 193, 241, 203, 217, 232, 7, 156, 63, 94, 200, 194, 91, 110, 173, 248, 42, 3, 134, 167, 47, 175, 87, 63, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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