Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c041e7783d239a73c2d620b9f583f9d35859fdffef760c51f0c1c9b6f5711f75

Tx prefix hash: 55b2495900f76cc91956cfb38c2ac1442c2366684ccefe2b581a58f31e4f0164
Tx public key: 065a01fe97cf7f7fe583d6c28d8321c3b7acdcf0a9226fe89fb798bfe625d4de
Timestamp: 1719891270 Timestamp [UCT]: 2024-07-02 03:34:30 Age [y:d:h:m:s]: 00:302:07:15:10
Block: 1056642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216064 RingCT/type: yes/0
Extra: 01065a01fe97cf7f7fe583d6c28d8321c3b7acdcf0a9226fe89fb798bfe625d4de0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8554adee5f95bcb318e15ccfb376d4ead4d926ddee3f5791754df1a4da039b0 0.600000000000 1527059 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": 1056652, "vin": [ { "gen": { "height": 1056642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8554adee5f95bcb318e15ccfb376d4ead4d926ddee3f5791754df1a4da039b0" } } ], "extra": [ 1, 6, 90, 1, 254, 151, 207, 127, 127, 229, 131, 214, 194, 141, 131, 33, 195, 183, 172, 220, 240, 169, 34, 111, 232, 159, 183, 152, 191, 230, 37, 212, 222, 2, 17, 0, 0, 0, 2, 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