Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fe2158604f283c8550e867f6b547d55823a69d3bf70cf5902261aaee25fed4f

Tx prefix hash: a80a2da5b5e5f6890df5653af71e69f7d2a7667fd50da0c1677d11b7d356de57
Tx public key: 943aeb2f7515dc3cb6375c2186c987ccffc2019ddfc2b937408975e4242d9778
Timestamp: 1701975028 Timestamp [UCT]: 2023-12-07 18:50:28 Age [y:d:h:m:s]: 01:124:17:50:23
Block: 908122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350300 RingCT/type: yes/0
Extra: 01943aeb2f7515dc3cb6375c2186c987ccffc2019ddfc2b937408975e4242d9778021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.601194233000 dcy

stealth address amount amount idx
00: 1775f4e029b85c50888b4cac9a260e5bd84593f2e1a210c879fecabeb2b0b8c1 0.601194233000 1365147 of 0

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": 908132, "vin": [ { "gen": { "height": 908122 } } ], "vout": [ { "amount": 601194233, "target": { "key": "1775f4e029b85c50888b4cac9a260e5bd84593f2e1a210c879fecabeb2b0b8c1" } } ], "extra": [ 1, 148, 58, 235, 47, 117, 21, 220, 60, 182, 55, 92, 33, 134, 201, 135, 204, 255, 194, 1, 157, 223, 194, 185, 55, 64, 137, 117, 228, 36, 45, 151, 120, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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