Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7aaee76f88b81333426fcfe00f296641e9cebd5be17cb914b1ba758a350b9d3d

Tx prefix hash: 33f14b6df47ea98c0ef81e3b9be974c64736ff60e4f54364fa20d4fc9cf38c2a
Tx public key: 25547ae90c6a3d99334874eb65b249e2d0b1630e7dc23ab29237898c442e3426
Timestamp: 1635028504 Timestamp [UCT]: 2021-10-23 22:35:04 Age [y:d:h:m:s]: 03:142:18:32:09
Block: 359111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 880150 RingCT/type: yes/0
Extra: 0125547ae90c6a3d99334874eb65b249e2d0b1630e7dc23ab29237898c442e34260211000000705410958b000000000000000000

1 output(s) for total of 39.638443560000 dcy

stealth address amount amount idx
00: 223ce62e4a5bd9db3c24260b77a247a69ae11f43896292d4855d06814b210d22 39.638443560000 731424 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": 359121, "vin": [ { "gen": { "height": 359111 } } ], "vout": [ { "amount": 39638443560, "target": { "key": "223ce62e4a5bd9db3c24260b77a247a69ae11f43896292d4855d06814b210d22" } } ], "extra": [ 1, 37, 84, 122, 233, 12, 106, 61, 153, 51, 72, 116, 235, 101, 178, 73, 226, 208, 177, 99, 14, 125, 194, 58, 178, 146, 55, 137, 140, 68, 46, 52, 38, 2, 17, 0, 0, 0, 112, 84, 16, 149, 139, 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