Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be6ac40d42236cc128182223e21f95eb454155dd7b531f98dbf13f3e8cbd4f69

Tx prefix hash: a1a2a83cdf7becf04295064e3a5d0ca46e0f87125848956fd5208fd00befeb20
Tx public key: 9e01b3a2ea2547d8ada741d78e0066107ddb9de00cd6187da293b3eb51a0c753
Timestamp: 1702903053 Timestamp [UCT]: 2023-12-18 12:37:33 Age [y:d:h:m:s]: 01:016:06:08:11
Block: 915812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272961 RingCT/type: yes/0
Extra: 019e01b3a2ea2547d8ada741d78e0066107ddb9de00cd6187da293b3eb51a0c75302110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46c5c400a2f2b9eb688140c6236082d3cf7056abc5cea387f87837c3ba097d82 0.600000000000 1373244 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": 915822, "vin": [ { "gen": { "height": 915812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46c5c400a2f2b9eb688140c6236082d3cf7056abc5cea387f87837c3ba097d82" } } ], "extra": [ 1, 158, 1, 179, 162, 234, 37, 71, 216, 173, 167, 65, 215, 142, 0, 102, 16, 125, 219, 157, 224, 12, 214, 24, 125, 162, 147, 179, 235, 81, 160, 199, 83, 2, 17, 0, 0, 0, 1, 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