Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 846707418c252baaf7031fac5c7446ac27ff2b2d7bf945dd0d2e5680c403f94c

Tx prefix hash: 5d7e946e42b1d37f6d9afc0ed9df867a414ae5892ee12dbd9bd2f40d7d357bc5
Tx public key: 4c2f80159c3003b7c6c30f2549fdd63044489f9768b23c66bb4e3b0b9643a6ef
Timestamp: 1697423086 Timestamp [UCT]: 2023-10-16 02:24:46 Age [y:d:h:m:s]: 01:100:23:00:09
Block: 870588 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333366 RingCT/type: yes/0
Extra: 014c2f80159c3003b7c6c30f2549fdd63044489f9768b23c66bb4e3b0b9643a6ef02110000000775e3f0e9000000000000000000

1 output(s) for total of 0.800535479000 dcy

stealth address amount amount idx
00: ff022a401f7ad9aa50740e1a89223f1a0f2d096c945017f3e694981b9a232797 0.800535479000 1325471 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": 870598, "vin": [ { "gen": { "height": 870588 } } ], "vout": [ { "amount": 800535479, "target": { "key": "ff022a401f7ad9aa50740e1a89223f1a0f2d096c945017f3e694981b9a232797" } } ], "extra": [ 1, 76, 47, 128, 21, 156, 48, 3, 183, 198, 195, 15, 37, 73, 253, 214, 48, 68, 72, 159, 151, 104, 178, 60, 102, 187, 78, 59, 11, 150, 67, 166, 239, 2, 17, 0, 0, 0, 7, 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