Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05cdfe916d8f9c93c2d2196ba1f9808dc546dcf7d8a064ad498ee6dc42765e0d

Tx prefix hash: a76c5c57edad1600dc659dbfa9a2d0ffdbd1b78501ba214e422f1235e7e45885
Tx public key: e425b42ce5e504d000801a3c77fe26ff21526022bff26c14a9ac2e22100bda1b
Timestamp: 1723206087 Timestamp [UCT]: 2024-08-09 12:21:27 Age [y:d:h:m:s]: 00:312:18:42:13
Block: 1084137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223358 RingCT/type: yes/0
Extra: 01e425b42ce5e504d000801a3c77fe26ff21526022bff26c14a9ac2e22100bda1b02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bbac19dd0e2d844cf97c89059b11b347260acc0d14d3dbe724469f2adf6d9df0 0.600000000000 1558300 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": 1084147, "vin": [ { "gen": { "height": 1084137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbac19dd0e2d844cf97c89059b11b347260acc0d14d3dbe724469f2adf6d9df0" } } ], "extra": [ 1, 228, 37, 180, 44, 229, 229, 4, 208, 0, 128, 26, 60, 119, 254, 38, 255, 33, 82, 96, 34, 191, 242, 108, 20, 169, 172, 46, 34, 16, 11, 218, 27, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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