Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 127897b01f719dd2832460f55681a1f414e3b2544be0f5dd8ee8a21f00bc2a80

Tx prefix hash: 9d80d5eac15239edd428d3aaba7be1220cac0bbe293d7efd048b978fb85145a6
Tx public key: 5ae576dc9733f1923096e36d60e99962fa248cf9fd2a22fa5fcdd52d7ae1215d
Timestamp: 1735114892 Timestamp [UCT]: 2024-12-25 08:21:32 Age [y:d:h:m:s]: 00:086:15:15:35
Block: 1182755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61689 RingCT/type: yes/0
Extra: 015ae576dc9733f1923096e36d60e99962fa248cf9fd2a22fa5fcdd52d7ae1215d021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b39e3d7152203e6a06610bedb4f7681b839286ae71b1b58e75659e5d4dd6ca1b 0.600000000000 1669194 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": 1182765, "vin": [ { "gen": { "height": 1182755 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b39e3d7152203e6a06610bedb4f7681b839286ae71b1b58e75659e5d4dd6ca1b" } } ], "extra": [ 1, 90, 229, 118, 220, 151, 51, 241, 146, 48, 150, 227, 109, 96, 233, 153, 98, 250, 36, 140, 249, 253, 42, 34, 250, 95, 205, 213, 45, 122, 225, 33, 93, 2, 17, 0, 0, 0, 2, 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