Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75e08000b2ba06ac110eae576b53f9b306ade1f89118e30424b02e3be87dbc53

Tx prefix hash: 5fb0e51332abf7ef76438052427f58838ab61f06a86e0bba85fe0d23ec4553a0
Tx public key: ae1b7def4d03212b37ca34ea09bb609681b2eb7203834f1c79cc47051f08e871
Timestamp: 1738044479 Timestamp [UCT]: 2025-01-28 06:07:59 Age [y:d:h:m:s]: 00:342:18:10:23
Block: 1206747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242801 RingCT/type: yes/0
Extra: 01ae1b7def4d03212b37ca34ea09bb609681b2eb7203834f1c79cc47051f08e871021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f539c6f66f59c8f6531e928c22b754e8cc41fbf1a2cfaafeb36df5591c962d74 0.600000000000 1693460 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": 1206757, "vin": [ { "gen": { "height": 1206747 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f539c6f66f59c8f6531e928c22b754e8cc41fbf1a2cfaafeb36df5591c962d74" } } ], "extra": [ 1, 174, 27, 125, 239, 77, 3, 33, 43, 55, 202, 52, 234, 9, 187, 96, 150, 129, 178, 235, 114, 3, 131, 79, 28, 121, 204, 71, 5, 31, 8, 232, 113, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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