Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13340c0deab66fe63391518bd4102cd2f667a11213cbca6828475c12110ea129

Tx prefix hash: fb633f3f3321e6b8a695569b4d859628dfd0f833071c20f55915c7b91bd3b033
Tx public key: a7a392289f60e03a8bb449e03910a9bdf8b1eb53184fbd4286bc2a0839cf7e9b
Timestamp: 1626664312 Timestamp [UCT]: 2021-07-19 03:11:52 Age [y:d:h:m:s]: 03:234:00:42:34
Block: 296660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 938617 RingCT/type: yes/0
Extra: 01a7a392289f60e03a8bb449e03910a9bdf8b1eb53184fbd4286bc2a0839cf7e9b021100000025ed79a617000000000000000000

1 output(s) for total of 63.832634054000 dcy

stealth address amount amount idx
00: 5767f33dc8f9440044ed088639c0b84af110c45a65e1ccf6dc8da2804ba1c15d 63.832634054000 620990 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": 296670, "vin": [ { "gen": { "height": 296660 } } ], "vout": [ { "amount": 63832634054, "target": { "key": "5767f33dc8f9440044ed088639c0b84af110c45a65e1ccf6dc8da2804ba1c15d" } } ], "extra": [ 1, 167, 163, 146, 40, 159, 96, 224, 58, 139, 180, 73, 224, 57, 16, 169, 189, 248, 177, 235, 83, 24, 79, 189, 66, 134, 188, 42, 8, 57, 207, 126, 155, 2, 17, 0, 0, 0, 37, 237, 121, 166, 23, 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