Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b12acc2a13936b4c1b1b8749a24af7066faf86ca51413cf6e9422844df869308

Tx prefix hash: f9edfcfef220747b69e69d2db940c4a4c436910814732dc42a8271e34f46196c
Tx public key: ea3142dae44fbdd81f177a28ae9d1a74af3e85711b7b2d5a4fe6d4d80bbe045c
Timestamp: 1675639081 Timestamp [UCT]: 2023-02-05 23:18:01 Age [y:d:h:m:s]: 01:287:13:03:57
Block: 690665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 466442 RingCT/type: yes/0
Extra: 01ea3142dae44fbdd81f177a28ae9d1a74af3e85711b7b2d5a4fe6d4d80bbe045c021100000001e6d27f9c000000000000000000

1 output(s) for total of 3.158930516000 dcy

stealth address amount amount idx
00: 5f193813abe5b32996f54d5e780089df2a0e20989fc11cd8f62f0eb7866d8b8f 3.158930516000 1133399 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": 690675, "vin": [ { "gen": { "height": 690665 } } ], "vout": [ { "amount": 3158930516, "target": { "key": "5f193813abe5b32996f54d5e780089df2a0e20989fc11cd8f62f0eb7866d8b8f" } } ], "extra": [ 1, 234, 49, 66, 218, 228, 79, 189, 216, 31, 23, 122, 40, 174, 157, 26, 116, 175, 62, 133, 113, 27, 123, 45, 90, 79, 230, 212, 216, 11, 190, 4, 92, 2, 17, 0, 0, 0, 1, 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