Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: daaaa8a116afb2afd278cb9811228e834eb9c929d61051da6402b1f49d06085d

Tx prefix hash: 67428532622bf4477e1ccf1a596432efa717b4f9c09b4d40230346d3fce4f824
Tx public key: b33183334e22773ff1c646b28e97ba109bbb91413758274b9b8d5b705fe317d8
Timestamp: 1639264801 Timestamp [UCT]: 2021-12-11 23:20:01 Age [y:d:h:m:s]: 03:174:01:36:56
Block: 393490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 903217 RingCT/type: yes/0
Extra: 01b33183334e22773ff1c646b28e97ba109bbb91413758274b9b8d5b705fe317d802110000000106faf294000000000000000000

1 output(s) for total of 30.493315378000 dcy

stealth address amount amount idx
00: 1cdc392291b3e5ff67ee2874f086af5fe0fb44259f25f7905cee2445c67c7a6d 30.493315378000 790747 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": 393500, "vin": [ { "gen": { "height": 393490 } } ], "vout": [ { "amount": 30493315378, "target": { "key": "1cdc392291b3e5ff67ee2874f086af5fe0fb44259f25f7905cee2445c67c7a6d" } } ], "extra": [ 1, 179, 49, 131, 51, 78, 34, 119, 63, 241, 198, 70, 178, 142, 151, 186, 16, 155, 187, 145, 65, 55, 88, 39, 75, 155, 141, 91, 112, 95, 227, 23, 216, 2, 17, 0, 0, 0, 1, 6, 250, 242, 148, 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