Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74c00e4f970e9550d73f7f17425c8995acd6512ff1c717600f41553f42436037

Tx prefix hash: 81d13fcc982a8ce9d84892ba170492e1d4f1e1d193c9e2115f05467d1eafd508
Tx public key: 50fbecfdddb589cf12d5cde03e1e05c0661ef59f72cb8c4a4a5f893d48e86d11
Timestamp: 1684325775 Timestamp [UCT]: 2023-05-17 12:16:15 Age [y:d:h:m:s]: 02:005:13:55:58
Block: 762050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 526122 RingCT/type: yes/0
Extra: 0150fbecfdddb589cf12d5cde03e1e05c0661ef59f72cb8c4a4a5f893d48e86d11021100000004e6d27f9c000000000000000000

1 output(s) for total of 1.832365868000 dcy

stealth address amount amount idx
00: 2b9e7b05abd1b2d190402b782eba927159d68da037d6bf663d5b57728d0f9b51 1.832365868000 1210761 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": 762060, "vin": [ { "gen": { "height": 762050 } } ], "vout": [ { "amount": 1832365868, "target": { "key": "2b9e7b05abd1b2d190402b782eba927159d68da037d6bf663d5b57728d0f9b51" } } ], "extra": [ 1, 80, 251, 236, 253, 221, 181, 137, 207, 18, 213, 205, 224, 62, 30, 5, 192, 102, 30, 245, 159, 114, 203, 140, 74, 74, 95, 137, 61, 72, 232, 109, 17, 2, 17, 0, 0, 0, 4, 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