Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49d324115094d65dc61af5da856d36fc7ee734561d5b9d1c055e09c448387476

Tx prefix hash: 8786b69a39cef5e818930f7ffb44aa294561255129b7f04fbbbf1858c2e89b8f
Tx public key: 8010312a706bdc9da90f89b826b1e7bbedd3d04c64ded78a31f40295c0d2e573
Timestamp: 1675517166 Timestamp [UCT]: 2023-02-04 13:26:06 Age [y:d:h:m:s]: 02:267:15:40:31
Block: 689655 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 710626 RingCT/type: yes/0
Extra: 018010312a706bdc9da90f89b826b1e7bbedd3d04c64ded78a31f40295c0d2e573021100000001e6d27f9c000000000000000000

1 output(s) for total of 3.183366371000 dcy

stealth address amount amount idx
00: 4549f5cf6c250e32e906c748753403fe9cf5c1cda2774b7d7b38724e92bb3760 3.183366371000 1132347 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": 689665, "vin": [ { "gen": { "height": 689655 } } ], "vout": [ { "amount": 3183366371, "target": { "key": "4549f5cf6c250e32e906c748753403fe9cf5c1cda2774b7d7b38724e92bb3760" } } ], "extra": [ 1, 128, 16, 49, 42, 112, 107, 220, 157, 169, 15, 137, 184, 38, 177, 231, 187, 237, 211, 208, 76, 100, 222, 215, 138, 49, 244, 2, 149, 192, 210, 229, 115, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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