Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b13ed9ba6b10d53852372222f5801a26ff4f966e9f15a82ce46e271ee52a649

Tx prefix hash: 2207cf4916eb1411dbc5785f7955272f3fa13adf57ef786a93abf674c2c3cb50
Tx public key: df308b63ed4f9e6164c5d3922a33823363b33dc7bd1a56390d544358ece5aab4
Timestamp: 1681180411 Timestamp [UCT]: 2023-04-11 02:33:31 Age [y:d:h:m:s]: 02:004:21:28:42
Block: 735956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 525659 RingCT/type: yes/0
Extra: 01df308b63ed4f9e6164c5d3922a33823363b33dc7bd1a56390d544358ece5aab402110000000275e3f0e9000000000000000000

1 output(s) for total of 2.236003535000 dcy

stealth address amount amount idx
00: e84eac3a5cbc5c100c60fbb4e8c7aa72162a7c7abf4b08e3bbe89afd8d61b34e 2.236003535000 1182329 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": 735966, "vin": [ { "gen": { "height": 735956 } } ], "vout": [ { "amount": 2236003535, "target": { "key": "e84eac3a5cbc5c100c60fbb4e8c7aa72162a7c7abf4b08e3bbe89afd8d61b34e" } } ], "extra": [ 1, 223, 48, 139, 99, 237, 79, 158, 97, 100, 197, 211, 146, 42, 51, 130, 51, 99, 179, 61, 199, 189, 26, 86, 57, 13, 84, 67, 88, 236, 229, 170, 180, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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