Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43c11f574c8724c462539df91640589e31ff1b0d73187d5232993a557f5fdd5c

Tx prefix hash: 7e9960809fe78604251b0476a5b2bb2852a708d58f8db374ff041063caa5144b
Tx public key: f39fdf250d3ba1ae787d00980408ed8fea9d8282b6502f0c875760e508f8167d
Timestamp: 1695701103 Timestamp [UCT]: 2023-09-26 04:05:03 Age [y:d:h:m:s]: 01:051:21:47:28
Block: 856305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298342 RingCT/type: yes/0
Extra: 01f39fdf250d3ba1ae787d00980408ed8fea9d8282b6502f0c875760e508f8167d02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.892701189000 dcy

stealth address amount amount idx
00: f6f6c6781da4e6ce0a6dbfc31ac80600e1f4ad6463183ddc858b9fc8777b7589 0.892701189000 1310373 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": 856315, "vin": [ { "gen": { "height": 856305 } } ], "vout": [ { "amount": 892701189, "target": { "key": "f6f6c6781da4e6ce0a6dbfc31ac80600e1f4ad6463183ddc858b9fc8777b7589" } } ], "extra": [ 1, 243, 159, 223, 37, 13, 59, 161, 174, 120, 125, 0, 152, 4, 8, 237, 143, 234, 157, 130, 130, 182, 80, 47, 12, 135, 87, 96, 229, 8, 248, 22, 125, 2, 17, 0, 0, 0, 4, 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