Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63fa42171cc43b412d1e939450db17e3e7fa32679b60ff64a6601eb0f3444f20

Tx prefix hash: 2d883f8becd1bed96a8df0ee4daf33b0d5e4def883a6aee53c26982e7aa9c2c7
Tx public key: 630f77173d7f0a2b905dfe36cf1ad12fcdf905c056262e0ad1408e2b234cdba5
Timestamp: 1716930519 Timestamp [UCT]: 2024-05-28 21:08:39 Age [y:d:h:m:s]: 00:315:14:37:22
Block: 1032124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225560 RingCT/type: yes/0
Extra: 01630f77173d7f0a2b905dfe36cf1ad12fcdf905c056262e0ad1408e2b234cdba50211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4b1fc6d0f77511397620e86e142d25558e45a9e5f851fb6c33b7b0cb3d20751 0.600000000000 1500573 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": 1032134, "vin": [ { "gen": { "height": 1032124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4b1fc6d0f77511397620e86e142d25558e45a9e5f851fb6c33b7b0cb3d20751" } } ], "extra": [ 1, 99, 15, 119, 23, 61, 127, 10, 43, 144, 93, 254, 54, 207, 26, 209, 47, 205, 249, 5, 192, 86, 38, 46, 10, 209, 64, 142, 43, 35, 76, 219, 165, 2, 17, 0, 0, 0, 6, 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